Create/update an issue per feature #7

foolip · 2025-06-13T10:11:45Z

No description provided.

scripts/update-issues.ts

Co-authored-by: Patrick Brosset <[email protected]>

scripts/update-issues.ts

foolip · 2025-07-15T08:38:55Z

I think this would work now. @captainbrosset care to review? In particular the issue template is important, and isn't very good yet.

Co-authored-by: François Daoust <[email protected]>

foolip · 2025-07-15T10:12:15Z

Seeing that it would "only" create ~300 issues I went ahead and triggered this in https://github.com/web-platform-dx/developer-signals/actions/runs/16290425578/job/45998890724 to shake out additional bugs. Issues are being created now.

foolip · 2025-07-15T10:17:57Z

I got the escaping wrong, deleting some code should fix that...

This should fix < in issue titles

foolip · 2025-07-15T11:04:57Z

Detecting open issues doesn't reliably work, debugging...

Update: fixed

rviscomi · 2025-07-23T19:03:02Z

scripts/update-issues.ts

+  await writeFile("manifest.json", manifestJson);
+  console.log('Wrote manifest.json');
+
+  // TODO: close open issues that were skipped / not updated.


Is this something that should be addressed now or later?

Not sure if it's what you had in mind here, but we should close issues for features that have since graduated to Baseline status, along with a clarifying comment.

On the flip side, if a feature regresses, we should reopen the existing issue to preserve the original upvotes.

Is this something that should be addressed now or later?

I intended to address it later, and basically just close any issues that we didn't put in the manifest. But I wanted to see which issues would be closed in practice before automating it, to see if the rule feels right. One could imagine a different rule for opening new issues vs. closing old issues, with a grace period of sorts.

On the flip side, if a feature regresses, we should reopen the existing issue to preserve the original upvotes.

This is a good point, and would require iterating closed issues as well. Unfortunately I've already made a mess of things with issues that I opened by accident due to a bug, which would lead to multiple issues found for some features. Maybe I could just edit all of those issues to be blank to avoid the problem.

Making a mess, while working on this script is not a problem. We can always just delete issues and start again.

Deleting the issues would be good to avoid having to deal with them in the future. @tidoust do you have admin rights to delete the 35 issues from #324 through #358? They are currently matched by this search.

scripts/update-issues.ts

captainbrosset · 2025-07-28T13:24:23Z

scripts/update-issues.ts

+
+For more details on this feature:
+
+${data.caniuse ? `- [caniuse.com](https://caniuse.com/${data.caniuse})` : ""}


These are good resources to point to. I would perhaps add a link to MDN too.
We have some mappings for this too at: https://github.com/web-platform-dx/web-features-explorer/blob/main/additional-data/mdn-docs.json

(soon at https://github.com/web-platform-dx/web-features-mappings/blob/main/mappings/mdn-docs.json)

Since there can be multiple MDN links for a feature, sometimes it's a list and each item needs a name of some sort. I see that in https://web-platform-dx.github.io/web-features-explorer/features/individual-transforms/ you went from "Web/CSS/transform-function/translate" to "translate()" and it seems like the code for that is here:

https://github.com/web-platform-dx/web-features-explorer/blob/3a8dba6acaaf49ed14393da2d6f50d0d88c18910/.eleventy.js#L180-L183

What do you think about publishing the titles as well so I don't need to have a dependency on @ddbeck/mdn-content-inventory?

Agreed. The new separate mappings repo does have the titles already.

OK, would you be OK with a TODO to add MDN links once web-features-mappings is on NPM?

scripts/update-issues.ts

captainbrosset · 2025-07-28T13:38:33Z

scripts/update-issues.ts

+  const ids = Array.from(manifest.keys()).sort();
+  const manifestJson = JSON.stringify(
+    Object.fromEntries(ids.map((id) => [id, manifest.get(id)])));
+  await writeFile("manifest.json", manifestJson);


Suggested change

await writeFile("manifest.json", manifestJson);

await writeFile("web-features-signals.json", manifestJson);

The word manifest makes me think of extensions, or PWAs. Sorry, can't help it. What do you think of this more descriptive name?

Also, I see that you're ignoring this file in .gitignore. What do we need it for then? If this is for another use case than just creating/updating issues, then I would move the logic to do this to another script.

Related to this, a file like this would definitely be useful for https://github.com/web-platform-dx/web-features-mappings at some point, so I'm pretty keen on having it, but in this case, I wouldn't ignore it from git.

I want to publish this file somewhere, that's the main remaining piece before this can be used on caniuse or MDN. Not sure if it should be published on NPM or as a GitHub release, or maybe GitHub pages, but I don't think it should be in the repo itself as the commit history would be completely dominated by that file.

But anyway, I'll rename it to web-features-signals.json now, that works for me.

captainbrosset · 2025-07-28T13:39:54Z

scripts/update-issues.ts

+  await writeFile("manifest.json", manifestJson);
+  console.log('Wrote manifest.json');
+
+  // TODO: close open issues that were skipped / not updated.


Making a mess, while working on this script is not a problem. We can always just delete issues and start again.

captainbrosset · 2025-07-28T13:41:31Z

scripts/update-issues.ts

+    }
+  }
+
+  // Sort features by earliest release date in any browser, using subsequent shipping


Why do we need to sort the features exactly? I'm not sure I follow.

It's not strictly necessary, but I wanted the issue list to be roughly chronological, with older features being created first, similar to what would happen if this script had been running for years already.

Now that the issues are already seeded I could just delete this. WDYT?

scripts/update-issues.ts

Co-authored-by: Patrick Brosset <[email protected]>

Create/update an issue per feature

0b0a11f

foolip force-pushed the issue-per-feature branch from 956766e to 0b0a11f Compare June 13, 2025 10:14

captainbrosset reviewed Jun 13, 2025

View reviewed changes

scripts/update-issues.ts Outdated Show resolved Hide resolved

Update scripts/update-issues.ts

57d6bf2

Co-authored-by: Patrick Brosset <[email protected]>

foolip mentioned this pull request Jul 14, 2025

Track feature upvotes over time #8

Open

foolip added 4 commits July 14, 2025 16:49

Skip features based on standards positions

57c5105

Fix issue_number when updating

34c0a43

Don't create issues for any Baseline features and log why

858e664

Fix TODO in error message

04a9586

tidoust reviewed Jul 15, 2025

View reviewed changes

scripts/update-issues.ts Show resolved Hide resolved

foolip added 3 commits July 15, 2025 10:37

Sort features by shipping dates

7716e87

Skip discouraged features

84dfd6c

Add more logging

37f01fc

foolip marked this pull request as ready for review July 15, 2025 08:38

foolip and others added 3 commits July 15, 2025 10:52

Apply suggestion from @tidoust

231f229

Co-authored-by: François Daoust <[email protected]>

Add simple instructions for upvoting

89ad60f

Add dry run mode

bf34e7b

Don't escape issue title

97a1b89

This should fix < in issue titles

foolip mentioned this pull request Jul 15, 2025

Status of this repo #4

Closed

foolip added 2 commits July 15, 2025 12:40

Make labels an array

38b722f

Log when issue is up-to-date

869d237

foolip added 5 commits July 15, 2025 18:33

Fail if there are multiple open issues for a feature

d0f4601

Remove regexp g flag to not save state between calls

abe69fa

Sort out labels params

0d9fe49

Bump web-features

10d4677

Write a manifest.json after updating issues

e46ee61

Skip any features not in web-features

eccd92d

foolip requested a review from captainbrosset July 23, 2025 14:39

rviscomi reviewed Jul 23, 2025

View reviewed changes

add daily schedule

e991941

foolip mentioned this pull request Jul 24, 2025

Another way to get web dev input: one-click intent button on MDN pages web-platform-tests/interop#980

Open

captainbrosset requested changes Jul 28, 2025

View reviewed changes

scripts/update-issues.ts Show resolved Hide resolved

scripts/update-issues.ts Outdated Show resolved Hide resolved

foolip and others added 9 commits August 12, 2025 12:09

Add TODO for web-features-mappings

eed3b43

Update scripts/update-issues.ts

3e5a2cb

Co-authored-by: Patrick Brosset <[email protected]>

Extract positionsToIgnore

ba42249

Align with plugin-throttling.js docs

4f162c3

Rename manifest.json to web-features-signals.json

e547121

Update scripts/update-issues.ts

24ba04e

Co-authored-by: Patrick Brosset <[email protected]>

Bump web-features

44b4d0b

Run npm audit fix

4cf80ff

Fix name field in body template

0441f2c


		For more details on this feature:

		${data.caniuse ? `- [caniuse.com](https://caniuse.com/${data.caniuse})` : ""}

	await writeFile("manifest.json", manifestJson);
	await writeFile("web-features-signals.json", manifestJson);

Create/update an issue per feature #7

Are you sure you want to change the base?

Create/update an issue per feature #7

Uh oh!

Conversation

foolip commented Jun 13, 2025

Uh oh!

Uh oh!

Uh oh!

foolip commented Jul 15, 2025

Uh oh!

foolip commented Jul 15, 2025

Uh oh!

foolip commented Jul 15, 2025

Uh oh!

foolip commented Jul 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

captainbrosset Jul 28, 2025 • edited by foolip Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

foolip commented Jul 15, 2025 •

edited

Loading

captainbrosset Jul 28, 2025 •

edited by foolip

Loading